Project Proposal Instructions with example code

In this assignment you will develop your initial concept note into a draft of a full project proposal. Treat this assignment as a “dry run” for developing a proposal for a grant or fellowship application, or for your Ph.D. prospectus.

Your proposal should include at least the following sections and information.

Front matter: Descriptive title, your name, date, reference to “SYS 7030 Time Series Analysis & Forecasting, Fall 2020”.

Abstract: A very brief summary of the project.

1 Introduction

Give a narrative description of the problem you are addressing, and the methods you will use to address it. Provide context:

• What is the question you are attempting to answer?
• Why is this question important? (Who cares?)
• How will you go about attempting to answer this question?

This work addresses the question: Why do people not use probabilistic forecasts for decision-making (Council 2007)?

2 The data and the data-generating process

Describe the data set you will be analyzing, and where it comes from, how it was generated and collected. Identify the source of the data. Give a narrative description of the data-generating process: this piece is critical.

Since these will be time series data: identify the frequency of the data series (e.g., hourly, monthly), and the period of record.

esales <- dbGetQuery(db,'SELECT * from eia_elec_sales_va_all_m') # SQL code to retrieve data from a table in the remote database
# str(esales)
esales <- as_tibble(esales) # Convert dataframe to a 'tibble' for tidyverse work
# str(esales)

# Reference: https://arrow.apache.org/docs/r/
# if(!('arrow' %in% installed.packages())) install.packages('arrow')
library(arrow)
write_feather(esales, "esales.feather")

# Close connection -- this is good practice
dbDisconnect(db)
dbUnloadDriver(db_driver)

3 Exploratory data analysis

library(arrow)

Attaching package: 'arrow'

The following object is masked from 'package:utils':

    timestamp

esales <- read_feather("esales.feather")

str(esales)

tibble [233 × 4] (S3: tbl_df/tbl/data.frame)
 $ value: num [1:233] 8282 7839 8889 9368 9209 ...
 $ date : Date[1:233], format: "2020-05-01" "2020-04-01" ...
 $ year : int [1:233] 2020 2020 2020 2020 2020 2019 2019 2019 2019 2019 ...
 $ month: int [1:233] 5 4 3 2 1 12 11 10 9 8 ...

3.1 Provide a brief example of the data, showing how they are structured.

print(esales)

# A tibble: 233 x 4
    value date        year month
    <dbl> <date>     <int> <int>
 1  8282. 2020-05-01  2020     5
 2  7839. 2020-04-01  2020     4
 3  8889. 2020-03-01  2020     3
 4  9368. 2020-02-01  2020     2
 5  9209. 2020-01-01  2020     1
 6 10038. 2019-12-01  2019    12
 7  9291. 2019-11-01  2019    11
 8  8757. 2019-10-01  2019    10
 9  9874. 2019-09-01  2019     9
10 10912. 2019-08-01  2019     8
# … with 223 more rows

# References: https://www.tidyverse.org/, https://dplyr.tidyverse.org/

esales %>%
  filter(year == 2019) %>%
  filter(value > 9000) %>%
  print()

# A tibble: 10 x 4
    value date        year month
    <dbl> <date>     <int> <int>
 1 10038. 2019-12-01  2019    12
 2  9291. 2019-11-01  2019    11
 3  9874. 2019-09-01  2019     9
 4 10912. 2019-08-01  2019     8
 5 11527. 2019-07-01  2019     7
 6  9903. 2019-06-01  2019     6
 7  9147. 2019-05-01  2019     5
 8  9466. 2019-03-01  2019     3
 9  9148. 2019-02-01  2019     2
10 10925. 2019-01-01  2019     1

esales %>%
  group_by(month) %>%
  summarise(mean = mean(value)) -> mean_esales_by_month

`summarise()` ungrouping output (override with `.groups` argument)

esales %>%
  mutate(sales_TWh = value/1000) %>%
  select(-value)

# filter(data object, condition) : syntax for filter() command

3.2 Plot the time series.

#Reference: https://ggplot2.tidyverse.org/

ggplot(data=esales, aes(x=date,y=value)) + 
  geom_line() + xlab("Year") + ylab("Virginia monthly total electricity sales (GWh)")

# install.packages("tsibble")
library(tsibble) # Reference: https://tsibble.tidyverts.org/articles/intro-tsibble.html

Attaching package: 'tsibble'

The following object is masked from 'package:lubridate':

    interval

esales %>% as_tsibble(index = date) -> esales_tbl_ts

print(esales_tbl_ts)

# A tsibble: 233 x 4 [1D]
   value date        year month
   <dbl> <date>     <int> <int>
 1 9576. 2001-01-01  2001     1
 2 7820. 2001-02-01  2001     2
 3 8070. 2001-03-01  2001     3
 4 7153. 2001-04-01  2001     4
 5 7224. 2001-05-01  2001     5
 6 8264. 2001-06-01  2001     6
 7 8896. 2001-07-01  2001     7
 8 9404. 2001-08-01  2001     8
 9 7753. 2001-09-01  2001     9
10 7272. 2001-10-01  2001    10
# … with 223 more rows

library(lubridate) # Make it easy to deal with dates

esales_tbl_ts %>% filter(month==3)

esales_tbl_ts %>% filter(month(date)==3)

esales_tbl_ts %>%
  select(date, sales_GWh = value) -> elsales_tbl_ts

print(elsales_tbl_ts)

# A tsibble: 233 x 2 [1D]
   date       sales_GWh
   <date>         <dbl>
 1 2001-01-01     9576.
 2 2001-02-01     7820.
 3 2001-03-01     8070.
 4 2001-04-01     7153.
 5 2001-05-01     7224.
 6 2001-06-01     8264.
 7 2001-07-01     8896.
 8 2001-08-01     9404.
 9 2001-09-01     7753.
10 2001-10-01     7272.
# … with 223 more rows

3.3 Perform and report the results of other exploratory data analysis

hist(elsales_tbl_ts$sales_GWh, breaks=40)

# install.packages("feasts")
library(feasts)

Loading required package: fabletools

elsales_tbl_ts %>% 
  mutate(Month = yearmonth(date)) %>% 
  as_tsibble(index = Month) -> vaelsales_tbl_ts


vaelsales_tbl_ts %>% gg_season(sales_GWh, labels = "both") + ylab("Virginia electricity sales (GWh)")

# install.packages('tsibbledata')
library(tsibbledata)

aus_production

aus_production %>% gg_season(Electricity)

aus_production %>% gg_season(Beer)

vaelsales_tbl_ts %>% 
  gg_subseries(sales_GWh)

# aus_production %>% gg_subseries(Beer)

vaelsales_tbl_ts  %>% filter(month(Month) %in% c(3,6,9,12)) %>% gg_lag(sales_GWh, lags = 1:2)

vaelsales_tbl_ts  %>% filter(month(Month) == 1) %>% gg_lag(sales_GWh, lags = 1:2)

vaelsales_tbl_ts %>% ACF(sales_GWh) %>% autoplot()

# if(!('fpp3' %in% installed.packages())) install.packages('fpp3')
library(fpp3)

── Attaching packages ────────────────────────────────────────────── fpp3 0.3 ──

✓ fable 0.2.1     

── Conflicts ───────────────────────────────────────────────── fpp3_conflicts ──
x lubridate::date()   masks base::date()
x dplyr::filter()     masks stats::filter()
x tsibble::interval() masks lubridate::interval()
x dplyr::lag()        masks stats::lag()

# decompose(vaelsales_tbl_ts)

vaelsales_tbl_ts %>%
  model(STL(sales_GWh ~ trend(window=21) + season(window='periodic'), robust = TRUE)) %>%
  components() %>%
  autoplot()

vaelsales_tbl_ts %>%
  mutate(ln_sales_GWh = log(sales_GWh)) %>%
  model(STL(ln_sales_GWh ~ trend(window=21) + season(window='periodic'),
    robust = TRUE)) %>%
  components() %>%
  autoplot()

vaelsales_tbl_ts %>%
  features(sales_GWh, feat_stl)

vaelsales_tbl_ts %>%
  features(sales_GWh, feature_set(pkgs="feasts"))

Warning: `n_flat_spots()` is deprecated as of feasts 0.1.5.
Please use `longest_flat_spot()` instead.
This warning is displayed once every 8 hours.
Call `lifecycle::last_warnings()` to see where this warning was generated.

4 Statistical model

4.1 Formal model of data-generating process

Write down an equation (or set of equations) that represent the data-generating process formally.

For the electricity sales data, maybe the process looks like:

\[ y_t = Trend_t X Seasonal_t X Residual_t \] \[ y_t = \beta_0 + \beta_1 t + \beta_2 m + \varepsilon_t \]

# ETS forecasts
USAccDeaths %>%
  ets() %>%
  forecast() %>%
  autoplot()

str(taylor)
plot(taylor)

If applicable: describe any transformations of the data (e.g., differencing, taking logs) you need to make to get the data into a form (e.g., linear) ready for numerical analysis.

What kind of process is it? \(AR(p)\)? White noise with drift? Something else?

Write down an equation expressing each realization of the stochastic process \(y_t\) as a function of other observed data (which could include lagged values of \(y\)), unobserved parameters (\(\beta\)), and an error term (\(\varepsilon_t\)). Ex:

\[y = X\cdot\beta + \varepsilon\] Add a model of the error process. Ex: \(\varepsilon \sim N(0, \sigma^2 I_T)\).

4.2 Discussion of the statistical model

Describe how the formal statistical model captures and aligns with the narrative of the data-generating process. Flag any statistical challenges raised by the data generating process, e.g. selection bias; survivorship bias; omitted variables bias, etc.

5 Plan for data analysis

Describe what information you wish to extract from the data. Do you wish to… estimate the values of the unobserved model parameters? create a tool for forecasting? estimate the exceedance probabilities for future realizations of \(y_t\)?

Describe your plan for getting this information. OLS regression? Some other statistical technique?

If you can: describe briefly which computational tools you will use (e.g., R), and which packages you expect to draw on.

6 Submission requirements

Prepare your proposal using Markdown. (You may find it useful to generate your Markdown file from some other tool, e.g. R Markdown in R Studio.) Submit your proposal by pushing it to your repo within the course organization on Github. When your proposal is ready, notify the instructor by also creating a submission for this assignment on Collab. Please also upload a PDF version of your proposal to Collab as part of your submission.

7 Comment

Depending on your prior experience, you may find this assignment challenging. Treat this assignment as an opportunity to make progress on your own research program. Make your proposal as complete as you can. But note that this assignment is merely the First Draft. You will have more opportunity to refine your work over the next two months, in consultation with the instructor, your advisor, and your classmates.

8 References

Council, National Research. 2007. Completing the Forecast: Characterizing and Communicating Uncertainty for Better Decisions Using Weather and Climate Forecasts. https://doi.org/10.17226/11699.